In recent years, agile software development methods have become increasingly popular throughout the world. Today there are a number of different agile methods and they all rest on the Agile Manifesto that was formulated in 2001 as a reaction to the traditional software processes.The aim of this thesis is to make a survey of some of the agile methods used today and to see how they are being used in practice. It consists of two parts: a literature study and an interview study with people working in the software business. First, a definition of agile methods is proposed and a number of different agile methods are described. Second, the interviews are being analysed with special focus on communication, collaboration, expectations and results.

I detta arbete undersöker vi likheter och skillnader av hur litteraturen respektive utvecklare beskriver begreppet agile. För att komma fram till ett svar på frågeställningen gör vi en litteraturstudie där vi genom att jämföra dem olika agila utvecklingsprocesserna tar fram kriterier för hur begreppet agile beskrivs. Därefter gör vi intervjuer med representanter för 12 olika företag. Resultatet från dessa intervjuer ger oss ett svar på hur utvecklare beskriver agile..

Agile as an idea was created in 2001 through the Agile Manifesto with focus on social relationships, communication and flexibility. This was a reaction to the traditional, hierarchical organization with the goal of restoring balance within organizations in the IT business. Today we can see a transit of Agile from the IT-industry to other industries and areas, such as HRM.There is a challenge in attempting to traditionally control a social idea such as Agile, and there is a lack of empirical studies of the organizational context and its effect on the interpretation of Agile in practice. This study is an attempt to connect Agile to the science of business administration.The purpose with this study is therefore to research the organizational contexts effects on the interpretation of Agile in practice, within IT and HRM. Where Agile is established or well known.To fulfill our purpose we chose social constructivism as our scientifically approach, and conducted 12 in-depth interviews.

Agile systems development has in recent years become very popular, and many companies today claims to be working agile. At the same time there are studies about agile system development that indicate that there are difficulties in fully adopting the agile way. The purpose of this qualitative study has been to examine how true Swedish IT-companies conduct their agile system development compared to agile theory, and we have specifically for the purpose of the study designed a framework that has been used as an analytical tool. The framework helped us to maintain a structured and objective approach when we examined the participating companies and their practices. The study showed that there were differences regarding how true to agile theory the different companies conducts their agile projects, and that the differences in part depends on how long the companies have been working agile.

Systemutveckling har på senare år rört sig mot allt mer flexibla metoder för att bedriva utveckling, ett agilt förhållningssätt vid systemutveckling i dagens IT-bolag är inte alls ovanligt. I takt med förändring av tillvägagångssättet har även ett moment inom testningen fått allt mer fokus: Testautomatisering. Vissa författare hävdar till och med att det inte går att bedriva agil systemutveckling utan att införa testautomatisering. Syftet med uppsatsen är därför att undersöka vilka utmaningar en testare inom de agila metoderna stöter på vid testautomatisering. Detta utförs med hjälp av intervjuer på fem olika företag av fem olika testare där de alla har en gemensam nämnare, att de jobbar agilt..

To assure good quality the software needs to be tested to find errors and to verify that the programme meets the customer?s expectations. Traditional methods are usually used in software development and means that a number of predetermined steps are followed. By using agile methods the development can more easily be adapted to the changes on the market. With these methods the testing is carried out continuously throughout the project.

This paper is a degree project on the C-level, 15 points at University West, Department of Business and IT dept. Informatics. This study is about agile methodology and its impact on IT projects. Requirements management is a process within an IT project, where customer has certain requirements that must be met by an IT system. The difference between the traditional and agile development is in the requirements management process and it can cause problems in a project.

Lean och Agile är två arbetsmetodsfilsofier utvecklade från produktion respektive IT. Denna rapport ämnar besvara hur dessa är relaterade och om filosofierna med fördel kananvändas inom motstående område. En teoretisk litteraturstudie har genomförts med sökningar i databaser efter relateradforskning. Detta gav en god inblick om de både områdena var för sig och även omanvändandet av Lean inom IT. Däremot saknades information om Agile inom produktion.

In recent time, agile methods have been devoted much attention, and the concept is widely used in the IT industry in particular. An increasing number of companies are interested in this way of working. The following report is the result of a study on the ability to create value for customers in business development through the use of agile methods. We ask what the advantages and limitations of agile methods are in the creation of customer value. Grounded Theory and an initial literature review was used to answer this question.

In recent time, agile methods have been devoted much attention, and the concept is widely used in the IT industry in particular. An increasing number of companies are interested in this way of working. The following report is the result of a study on the ability to create value for customers in business development through the use of agile methods. We ask what the advantages and limitations of agile methods are in the creation of customer value. Grounded Theory and an initial literature review was used to answer this question.

This paper is a degree project on the C-level, 15 points at University West, Department of Business and IT dept. Informatics. This study is about agile methodology and its impact on IT projects. Requirements management is a process within an IT project, where customer has certain requirements that must be met by an IT system. The difference between the traditional and agile development is in the requirements management process and it can cause problems in a project.

Detta arbete är ett examensarbete på C-nivå, 10 poäng vid Luleå Tekniska Universitet, avd. Data och Systemvetenskap. Arbetet behandlar traditionell systemutveckling jämfört med Agile tänkandet. Detta sker genom en jämförelse av vilka olika faktorer som påverkar utvecklingsprocessen tidsmässigt i vattenfallsmodellen jämfört med Extrem Programmering. Vi har identifierat tiden som en av faktorerna vilka bidrar till att många projekt misslyckas under traditionella systemutvecklingsprocesser.

In a dynamic and unpredictable reality, either rigid structures or silo architectures areappropriate ways to organize an agile organization. This thesis enlightens these relationsbetween Service Oriented Architecture (SOA) and an organization who acts in a varied andconstantly changing business environment. In other words, this thesis enlightens the question:?How suitable is SOA to organize the enterprise who will meet a constantly changing andheterogenic business environment?.The thesis presents a model where an efficient organization must be agile to be able to actquickly in the business environments with constantly changing desires, needs, expectations,desires etc. According to the same model a Service Oriented Architecture organizes theenterprise elements such as processes, resources, competences, responsibilities, informationsystems etc.

The Thesis purpose is in the context of system development validate the Scrum Methodology. Projects concerning information technology are difficult to manage and tend to fail in quality, time or costs. Scrum presents a new view of the system development. Better cooperation between customers and developers, continuous follow-up on daily basis and extensive communication in the development team are all characteristics of Scrum. Scrum is described as a new paradigm by its founders but has been criticized by experts of system development too.

The aim with this thesis is to investigate two different methods used to test usability on web-sites to determine the advantages and disadvantages of two methods and compare the results. The two selected methods are the think aloud method and asynchronous remote method. Re-mote usability testing has existed for more than ten years but the possibilities with this meth-od needs to be explored more.To achieve the purpose of this thesis a case study was conducted on an e-commerce site and for the online remote usability testing software was used.The results of this study show that think aloud usability testing encounter more issues with the website than the remote usability testing..